[% setvar title Perl 6 should support I18N and L10N %]
<div id="archive-notice">
    <h3>This file is part of the Perl 6 Archive</h3>
    <p>To see what is currently happening visit <a href="http://www.perl6.org/">http://www.perl6.org/</a></p>
</div>
<div class='pod'>
<a name='TITLE'></a><h1>TITLE</h1>
<p>Perl 6 should support I18N and L10N</p>
<a name='VERSION'></a><h1>VERSION</h1>
<pre>  Maintainer: Simon Cozens &lt;<a href='mailto:simon@brecon.co.uk'>simon@brecon.co.uk</a>&gt;
  Date: 25 Sep 2000
  Mailing List: <a href='mailto:perl6-internals@perl.org'>perl6-internals@perl.org</a>
  Number: 313
  Version: 1
  Status: Developing</pre>
<a name='ABSTRACT'></a><h1>ABSTRACT</h1>
<p>Erreur de syntaxe. Syntaxfehler. Errore di sintassi. suntaktik'o sphalm'a.</p>
<a name='DESCRIPTION'></a><h1>DESCRIPTION</h1>
<p>Perl 6 needs some kind of internationalisation and therefore message
catalogue support. Really needs, with great urgency.</p>
<p>Whether we use GNU gettext or do our own thing, doesn't matter. Both the
Perl 6 binary and the standard library will be effected, meaning we'll
have to implement message catalogues both in C and in Perl. At least
internationalising the standard library will mean we can set an
example to CP6AN authors and so on.</p>
<a name='IMPLEMENTATION'></a><h1>IMPLEMENTATION</h1>
<p>Bring an XS (or equivalent) message catalogue library into the core so
that both the internals and the standard library can be localised.
Go about development with internationalisation in mind.</p>
<a name='REFERENCES'></a><h1>REFERENCES</h1>
<p><a href='http://turnbull.sk.tsukuba.ac.jp/Tools/I18N/LJ-I18N.html' target='_blank'>turnbull.sk.tsukuba.ac.jp</a></p>
</div>
